All rights reserved. This document is not to be printed in whole or in part without prior written consent of BCOM COMPUTER.
Disclaimer:
This software and documentation contains valuable trade secrets and proprietary information. Unauthorized use of this software or documentation may result in civil damages and/or criminal prosecution. BCOM COMPUTER believes that this documentation is accurate and accurately depicts the software's behavior but assumes no responsibility for its use, nor for any rights of third parties who may lawfully become entitled to, and do use the software or documentation contained herein.
BCOM QUEFILE TM and BCOM QUEFAX TM are both trademarks of BCOM COMPUTER.
BCOM COMPUTER , as well as BCOM QUEFILE or QUEFAX may be represented in this document as BCOM.
Information in this document is subject to change without notice and does not represent any commitments on the part of BCOM COMPUTER. This document is copyrighted and is protected by law. It is against the law to copy the software onto any medium except as allowed under a purchased license version or under a nondisclosure agreement. No part of this manual may be reproduced or transmitted in any form or by any means including, photocopying, electronic scan, mechanical, or video for any purpose without expressed written permission from BCOM COMPUTER.
BCOM COMPUTER respects and acknowledges the hard work of many other comapanies and individuals to obtain Copyrights and Trademarks:
COPYRIGHT AND TRADEMARK ACKNOWLEDGEMENTS:
* Microsoft« and MS-DOS are registered trademark of
Microsoft Corporation.
* WindowsTM is a trademark of Microsoft Corporation.
* True TypeTM is a trademark of Apple Computer, Inc.
* Hayes« is a registered trademark of Hayes
Microcomputer Products Inc.
* MNP« is a registered trademark of Microcom Inc.
* BCOM QueFileTM for WindowsTM acknowledges "for WindowsTM"
states: "for the Microsoft WindowsTM operating system".
* All or any other company names and/or products listed
are trademarks (TM), registered trademarks («), or
copyrights (⌐)of their respective owners.
Thank you,
__________________________________
Brent Jamerson
BCOM COMPUTER President
Thank you for your purchase of BCOM QUEFILE for Windows!
If you enjoy BCOM QUEFILE please tell all your friends. If you don't, please tell me why! Call or write me:
BCOM COMPUTER
c/o Brent Jamerson
2241 Jackson Circle
Carrollton, Texas 75006
Automated Voice/Fax/Data
214-245-4017
BCOM Computer was established in 1988 and is committed to excellence. I would be happy to receive any comments you have about any BCOM product.
Thanks again,
Brent.
BCOM QUEFILE is a complete communications package for the Microsoft Windows operating system. It is based on ease of use, and yet it provides users with a powerful array of communications tools. BCOM QUEFILE shareware version has some limited functionality. BCOM QUEFILE currently has 3 editions:
1. Shareware Starter Edition.
( Very limited functionality, no installation,
not serialized or registered software and its free! ).
2. Starter Edition Limited.
( Some functionality missing/reduced ).
3. Full-Functioning Edition.
BCOM QUEFILE Full-Functioning Edition when purchased, contains:
1. A full Windows hosted installation utility and compressed file format.
BCOM QUEFILE requires Microsoft Windows 3.1 enhanced mode.
BCOM QUEFILE requires an HAYES« "AT" compatible modem.
BCOM QUEFAX requires an HAYES« "AT" , Class 2 Group 3(class 1 is NOT supported) compatible fax-modem.
BCOM QUEFILE requires approximately 240k bytes of memory.
BCOM QUEFAX requires approximately 100k bytes of memory.
BCOM QUEFAX requires ~MegaBytes to load image files depending on the bitmap file and how many colors are in its palette.
BCOM QUEFILE uses approximately 1 Meg of disk space.
BCOM QUEFAX requires ~48k Bytes of disk space per fax image received. Send fax .BSF files require 216k bytes per page.
BCOM QUEFILE requires a mouse. Every effort has been made to ensure that TAB-STOP and ALT-KEY support were added but a couple of features may not be easily accessed or accessed at all.
It is strongly recommended that you use BCOM QUEFILE with a mouse.
BCOM QUEFILE Main Window
Once BCOM QUEFILE is up and running, it's title bar reflects the communication port values in use. It's setup like the DOS mode command. There is a number in brackets [] after BCOM that shows which instance 0-9 of BCOM QUEFILE this is. For more information see "Running Multiple Instances" later!
BCOM QUEFILE Quick Product Summary
o Based on ease of use, easier set-up than any other package!
- Select a modem and go! Built-in support for over 100 modems, Hassle free set-up, not intimidating like other packages!
- Targeted to users tired of communications hassles, Toolbar ( button bar for quick & easy feature access ).
o Class 2 Group 3 Fax Modem Support.
- Send and receive faxes using your fax modem. Send faxes to regular fax machines and remote fax modems.
- View, Print, Scale, received faxes. Use the clipboard. Custom cover pages and lots, lots more!
o Context sensitive help, BCOM is fully documented.
- Get help from most anywhere by pressing the F1 key.
- BCOM QUEFILE is fully documented.
o Single or multiple communication ports supported.
- Multi-Instance support ( multiple BCOM QUEFILE may run concurrently using shared code ).
o Full duplex asynchronous terminal support.
- Full screen (up to 100 lines)ANSI and limited VT100 emulation.
- Both embedded BCOM True TypeTM OEM scalable font and OEM Stock font supported.
o Eight (8) blazing fast file transfer protocols supported. Use the Windows Drag and Drop feature to send files!
- KERMIT *
- XMODEM *
- YMODEM * note1
- YMODEM BATCH * note1
- YMODEM-G option * note1
- YMODEM-G option BATCH * note1
- ASCII note1
- BINARY note1
note1, BCOM automatically negotiates BATCH
*Talk (chat) supported during file transfer from BCOM-to-BCOM.
o Multi-User Host Mode.
- Remote users have Login/Password/and DOS command level password support.
- Host Mode serves remote users via remote menu system.
- Chat, Login banner support, user messages. DOS level commands supported: TYPE,DIR,CD,RD,DEL,COPY,etc.
o Dial Directory and BBS dialer.
- Up to 100 saved users each with com port and dial set-up.
- A "NotesFile«" ( text ) can be tagged to any dial entry.
- Multiple supplement dial strings, BBS dialer and dial entry tag support.
o Script support for automating redundant communication chores like automated dialing, send/receive files, logon/logoff and more!
o QueFile allows users to schedule complex automated file transfers without the use of scripts to other BCOM users.
- Automatic save and restore of the scheduled file transfer queue.
o Audio sound board support.
- ".WAV" file support for multiple BCOM QUEFILE events!
o Clipboard support allows the user to copy screen data to the clipboard and paste clipboard data directly to the communications port!
o Advanced DDE support ( Dynamic Data Exchange ) provides a Client/Server programming interface to BCOM QUEFILE!
- A sample client DDE application and source code are provided!
o Many more extras! The BCOM advantage.
System Requirements: WindowsTM version 3.1, Mouse, Disk Space 1Meg, Memory 320K., Compatible Hayes« AT command set modem.
Enhacements: Audio Board with .WAV support. BCOM QUEFAX requires a class 2 Group 3 Hayes« compatible AT fax-modem.
BCOM QUEFILE Quick Feature Summary
Categorized by pull-down menu!
BCOM QUEFILE currently has the following list of features:
- FILE
o Send File
Contains all windows and dialog boxes to transmit a
file to a remote user. This also includes protocol
and file options.
o Receive File
Contains all windows and dialog boxes to receive a
file from a remote user. This also includes protocol
and file options.
o Capture File
Capture sent/received communications port data to a
file.
o Exit
Quits BCOM and exits back to Windows.
- DIAL
o Dial Directory
Allows user to enter, update, store, and dial
other users automatically. An additional feature allows
users to tag a notes file to dial entries!
o BBS Dialer
Selected dial directory users may be grouped into
a BBS user class, where BCOM can rotary dial
until a connect string is found. BCOM will then
terminate the BBS Dialer and stay on-line.
o Notify Beeps
User may select terminal to beep every 2 seconds once
a modem connect has been established.
- CONFIGURE
o Com Ports
Lets user setup communication port information like baud
rate, parity, number of data bits, modem type and more.
o Find Your Modem Port
BCOM QUEFILE will ask you to run this at initial
start-up. This option allows BCOM to automatically find
the port your modem is attached automatically.
o Flow Control (toggle)
Hardware CTS/RTS or Software XON/XOFF flow control
to/from modem. This is important for MNP modem users,
HARDWARE FLOW MUST USUALLY BE ON.(This is the default! )
o Modem Connect Type (toggle)
Modem or NULL-Modem. Modem connection is the default but
null-modem is helpful when using two computers
connected with only null-modem connecter.
o DTR or +++ RESET (toggle)
Select either DTR transition ( for this option your modem
must support "AT&D2") or "+++", to move your
modem off-line when in session. You may select the
slower "+++" option if your modem does not support
DTR transition.
o Set Strings
Allows the user to configure most string configured
items in BCOM QUEFILE. Like the modem reset string,
host password, etc.
o Quick View
Allows the user to quickly display various
menu setup options that are not viewable except
by traversing menus looking at them. The view is
displayed to the canvas.
o Bells and Whistles and .Wav support(toggle)
Configure sound, beeps, etc. ON/OFF.
o Host Users
Configure up to 100 host users for BCOM QUEFILE
Host Mode.
o Security
Not available.
o Toolbar ( also Button Bar )
Enable/Disable for graphics button bar support
( fast access to menu pull-downs items ).
o Save Configuration
Saves entire BCOM configuration to disk.
- SESSION
o Modem Init String
A quick way to send the modem init string to modem.
This string is configured under CONFIGURE, set strings.
o Modem Reset String
A quick way to send the modem reset string to modem.
This string is configured under CONFIGURE, set strings.
o Host Mode
Allows authorized remote users to dial into your
un-attended computer and even access DOS level commands
and file transfer. Built-in menus guide the remote
user throughout the Host Mode session. Host Mode is
secured with userid, password and DOS password
protection.
o Auto Answer String
Quick way to send the host initialization string to
the modem.
o A FAST 19200:N:8:1
Quick way to reinstall BCOM to new configuration settings.
o B FAST 19200:E:7:1
Quick way to reinstall BCOM to new configuration settings.
o C FAST 9600:N:8:1
Quick way to reinstall BCOM to new configuration settings.
o D FAST 9600:E:7:1
Quick way to reinstall BCOM to new configuration settings.
o Script
Execute a prepared script. Users can make text file
scripts that allow automated dialing, file send/recv,
host mode, etc, and logon and logoff to other computers.
o Offline + Reset Modem
Quick way to send DTR/+++ (offline) and the modem
reset string to modem.
- TERMINAL
o ANSI Emulation
If enabled, you allow BCOM to use "esc[" ANSI info
for screen addressing and color.
If disabled, you will see all ANSI escape sequences and
disable color and screen addressing support.
o Optional Emulators
Not available currently. Coming Soon.
o Echo
Allows user to see characters typed even when remote
host does not echo back.
o CRLF/CR
Carriage return Line feed/ Carriage return translations.
If CRLF/CR option is set to CRLF a CR from remote user
is translated into a New Line and a Carriage return.
o Color
When used in conjunction with ANSI Emulation, full ANSI
color support is available to your BCOM QUEFILE session.
o TTF/OEM Stock Font
The user may select True Type (scalable) font or choose to
use the OEM Stock font (fixed pitch) supplied
by Windows.
o Copy Area to Clipboard
The user enables or disables text screen data to be
marked with the mouse and sent to the Windows clipboard.
o Paste Clipboard to Port
If enabled ( not grayed ), the user may paste text data
from the clipboard to the configured BCOM
QUEFILE communications port.
o F1 Help/Sent
Upon the user pressing the F1 key its either:
1. Used to call the BCOM QUEFILE on-line help facility.
2. Sent to the com port
o SnapHeightTo24
Allows OEM Stock Font users to quickly snap the canvas
height to the standard 24 line display. It is especially
important to have 24 line display when connected to an
remote ANSI computer that is interactive (requiring use
of arrow keys, left, right, up, down). For example, a menu
that allows you to TAG files. The True Type Font always
re-sizes to 24 lines.
o Cursor Home
Clears the canvas and homes the cursor to location 0,0
(the upper left corner).
o Clear Screen
Clears the canvas.
- QUEFILES
o Schedule
Allows user to send/receive files between BCOM NODES
ONLY, on a scheduled basis. Queued files on a
configured date and time, can execute file transfer
to remote BCOM node left in Host Mode automatically.
A file specification , send/receive direction, date/time,
and the remote users primary password are tagged to a
dial directory entry. The QueFile entry is launched on a
timer basis and the session is completely automatic:
1. The number is auto-dialed until connected.
2. The file(s) will then be transferred.
3. BCOM then hangs-up and logs the transaction.
o Enable (default)
Allow remote BCOM users to use your host mode for
their initiated QueFiles. You may also toggle this
to disable.
o Save Queue to disk
User may store QueFile entries to disk. BCOM uses
a reserved file name of BCOMWINx.QUE. This allows large
amounts of scheduled file transfer entries to be stored
and reloaded. Users may also send .que files to other BCOM
nodes for scheduled file distribution and fan-out.
o Get Queue from disk
User may restore saved QueFile information from disk.
BCOM uses a reserved file name of BCOMWINx.QUE.
o Auto-Load at start-up
User may elect to have BCOM QUEFILE reload saved
QueFile information from disk at start-up.
This way QueFile entries may be restored to their
previous state from the last BCOM QUEFILE session.
Also, this option saves QueFile entries to disk when they
change status, thus totally automating the scheduled file
transfer queue.
o Protocol
Lets the user select which protocol to use when initiating
QueFile transfers. You must manually save your
configuration after selecting the protocol in order for
BCOM to use during the next BCOM QUEFILE session.
- INTERNAL
o Debug/Queue
Debug screen position, character size, modem response
strings and more.
o Clear Queue(s)
Manually clear out queued events before or while
they happen. All BCOM WINDOW events ( like host
mode, dial, script, file transfer, etc. ) are
queued. This means it possible to stack events.
Clear queue(s) will kill all outstanding events.
o List Queue(s)
List next 20 BCOM QUEFILE queued events.
- HELP
o Index
for BCOM QUEFILE Help. Can also be reached
by pressing F1 anywhere in BCOM QUEFILE!
o Using Help
Allows users unfamiliar with Windows help
facility to understand Windows Help procedures.
( Very good place for new users to start ).
o About BCOM...
Displays program information about BCOM QUEFILE,
like version, etc.
Running Multiple BCOM QUEFILE Instances
It is possible to have multiple copies of BCOM running on Windows concurrently. Each copy of BCOM QUEFILE running is called an instance. Please refer to your Windows Users Guide for more information on making additional copies of program manager group items. Each BCOM instance should have its own configuration (.CFG) and (.DAT) file. The instance is reflected from the command line argument invoked (Instance 0 is the assumed default if no argument is given) example:
WIN bcomwin.exe 2
This would result in the following BCOM QUEFILE title bar:
BCOM [2] COMx:XXXX:N,8,1
You may enter command line parameters using program manager.
Just select the BCOM Icon and under FILE properties:
\DIR\BCOMWIN.EXE 3
This would result in the following BCOM QUEFILE title bar:
BCOM [3] COMx:XXXX:N,8,1
Also, BCOM QUEFILE configuration files inherit the instance number. The file BCOMWIN0.CFG reflects instance 0 of a BCOM QUEFILE configuration file. BCOMWIN1.CFG would be the next instance and so on. You may have up to 10 ( 0-9 ) instances of config files. Remember, if two instances of BCOM attempt to share the same config file you will receive port open errors upon BCOM start up. Simply setup the next instance on a different port.
You CAN have them all share the same set of configuration files but it is not advised.
Multi-instance code design is simply another BCOM difference. It allows the user to SHARE CODE segments under Windows which allows the user to save a lot of memory. Each BCOM instance however requires it's own data segment (to keep separate copies of information like phone numbers etc.).
Using an NULL-MODEM connector, it is simple to make 2 instances of BCOM QUEFILE using COM1 and COM2 to connect on the same PC for demonstration reasons.
BCOM QUEFILE Getting Started
Quick Start
AT ANY POINT WHILE USING BCOM QUEFILE YOU MAY RECEIVE ON-LINE HELP! Press the [ F1 ] key for Help! BCOM also implements CONTEXT SENSITIVE HELP. An example of context sensitive help would be pressing F1 from a menu or dialog box and receiving specific help information on that topic.
o Please take time to read this document, it will help you to understand concepts for file transfer and specific implementations and features BCOM has included to make communications easier.
o If you know Windows and communications packages well, this document should be an easy overview, else read this entire document.
o BCOM generates internal messages that are useful for the user to track. For example, if the terminal is beeping and you don't know why, view the screen for "BCOM MESSAGE: <text>".
o BCOM QUEFILE may be run without a mouse, but a couple of features may not be easily accessed or accessed at all. We have made every attempt to make all panels accessible. It is strongly recommended that you use a mouse.
o All BCOM products generate their own configuration/data files.
Current BCOM QUEFILE file types:
.CFG Configuration information
MODEM.CFG is a list of supported modems.
.DAT Data information for phone book.
.HLP Help file information.
.DOC Documentation.
.WAV Audio board WAV files.
.EXE Executable.
.Nxx Where xx is 00-99 Dial Notes.
.BCM script files.
.HST Host display files.
.INI Information supplied files.
.ME Read these files first.
.xx_ Compressed files only if purchased
BCOM QUEFILE and supplied
with install.exe.
.PSW Generated by entering host users.
Contains userids,and passwords.
.nnn Where nnn is a BCOMWINx.nnn number
from 000-999 host message number.
.MSG BCOMWINx.MSG contains the highest
host message number to date.
.QUE QueFile entry save file name.
.\HOST Directory for host mode.
Current BCOM QUEFAX file types:
.TIF Tagged Information Format graphics
files.
.BMP Native Microsoft Bitmap graphics
files.
.BSF BCOM Send Fax format files.
.\FAXIN Directory for received faxes.
.\FAXOUT Directory for send faxes.
Installing BCOM QUEFILE
BCOM for Windows is distributed under several limited versions known as Starter Editions. The Starter Editions have reduced functionality where BCOM will gray menu strings out and provide pop-up dialog boxes which explain that a feature is not supported. To avoid this please purchase the full-functioning version ( see the LICENSE.ME file in the installation directory).
Starter Edition shareware users are provided with no installation utility. Please UNZIP your BCOM QUEFILE files all into the same directory ( i.e. PKUNZIP BCWIN2xx.ZIP D:\BCOMWIN ). You must now manually make a Program Manager group and item for BCOMWIN.EXE ( Refer to the Program Manager section in your Windows Users Guide). BCOM will adjust your WIN.INI parameters upon invocation.
o If you have purchased BCOM QUEFILE, follow any supplemented directions on the READ.ME file on the installation disk, then run INSTALL.EXE. You must install BCOM QUEFILE files, they are compressed on the distribution disk. You may install BCOM QueFile for Windows from within Windows or from MS-DOS.
Installing from within Windows: from the Windows Program Manager (or equivalent) using the File and Run option (Refer to the Program Manager section in your Windows Users Guide). Supply the RUN dialog box with both the floppy drive A: or B: where the BCOM installation disk is located and append \INSTALL.EXE. Example: A:\INSTALL.EXE.
Installing from MS-DOS: from the MS-DOS prompt, log the installation floppy drive A: or B: where the BCOM installation disk is located. Now type WIN INSTALL.EXE. This will load Windows and run INSTALL.EXE.
BCOM will automatically make a Program Manager group "BCOM" and an item for BCOMWIN.EXE, FAXMGR.EXE and DDE.EXE. BCOM will adjust your WIN.INI parameters upon invocation of BCOMWIN.EXE.
o Should you experience trouble with the install process: BCOM expects the home directory for BCOM QUEFILE to be placed in \WINDOWS\WIN.INI file under the "[BCOM]" category and use the "dir" option. BCOMWIN.EXE will attempt to make this modification for you during the initial comm port initialization. All BCOM executable and support files should be located in this directory, as BCOM expects to read them from this start-up directory. BCOM will return to this directory and drive when ever it writes configuration data back to disk.
NOTE: WIN.INI Parameters
[BCOM]
dir=c:\windows\bcomwin
o If you are re-installing BCOM QUEFILE, we encourage you to install BCOM QUEFILE over any existing versions. BCOM QUEFILE will not delete your existing BCOM configuration files. You will save disk space and always know where the latest version is.
o BCOM is distributed without .DAT/.CFG files so when BCOM first comes up it will not find the .CFG file. This makes BCOM initially ask user for COM port configuration under the BCOM INIT window. This only happens when BCOM cannot find the .CFG file. By saving the .CFG file (under CONFIGURATION pull-down), BCOM will not ask for initialization parameters unless requested to under the CONFIGURATION pull-down.
Except upon the initial install, BCOM will never save the .CFG file unless explicitly told to do so under configure pull-down or by using the SAVE CONFIG button on the button bar (arrow to harddisk).
o BCOM distributes a sample host mode welcome file (.HST). This will be displayed to Host Mode users if placed in the Host\Download directory (see Configure/Set Strings).
o Start BCOMWIN.EXE, double click on the ICON shown below.
Quick Start Continued...
o Fill in the requested COM PORT configuration information.
o Now try the following test BCOM modem sanity test:
Menu Section Formats And Conventions
Section arrangement for the remainder of this document is:
Line delimiter
Menu bar pull-down option
Menu functions
Menu function text
KEYS:
NOTE: If an ICON (example left) is present at the start of any menu item, the ICON represents this menu function on the button bar/toolbar.
BOLD type indicates an intense emphasis on a topic.
UNDERLINE and ITALIC type are used for emphasis when needed.
NOTE: When you see the this sign, pay particular close attention to the text immediate following.
C HINT: When you see the this sign, the text immediate following will point out some especially positive aspect of the particular topic.
D TRAP: Avoid these! When you see the this sign, the text immediate following will point out a problem, or some especially negative aspect of the particular topic.
The Toolbar and the term "button bar" may be used interchangeably.
File Pull-down
Send File(s)
Send File(s) to a remote user. Select a file transfer protocol from the first dialog box. Protocols are a predefined way for computers to send and receive data without data errors* (*except ASCII/BINARY). Choose from:
1. Xmodem (old but widely used, 128 byte packets).
3. Ymodem-G Batch (128-1024 mixed packets, only for file
transfer with error correcting/MNP style modems).
4. Kermit, added for compatibility with mainframes and
host computers (high overhead, use other protocols
when possible).
5. Ascii/Binary (straight file send, no protocol or
error checking).
The send protocol must match the remote's receive protocol exactly in order for file transfer to be successful.
* * * * * * * * * * * *
If you have questions as to which protocol to use,
read the BCOM file transfer protocols explained section!
BCOM will then advance the user to another dialog box, BCOM GET FILE NAME , that allows you to enter a file, set of files, or quit. This dialog box allows the user to select a file name or enter wildcards (more about wildcards later). The user may also change directories or disk drives. The user may elect to filter the available file types by using BCOM predefined filters( *.ZIP, *.EXE, etc) using the "List Files of Type" combo box (bottom left).
A file name edit box is supplied for cases where the user wants to type the file specification (like c:\autoexec.bat) or enter wildcards (like *.*, *.exe, *.??? etc.). XMODEM is the only BCOM QUEFILE protocol incapable of sending/receiving multiple files, hence no wildcards ( * or ? ) allowed.
If wildcards are used with XMODEM, only the first available type file found will be used! The file or file specification must appear in the file name edit box before BCOM can continue by clicking "OK". If at this point you wish to cancel the file transfer, just click "CANCEL".
Now the last file transfer WINDOW comes up, the BCOM FILE TRANSPORT WINDOW. BCOM is ready to transfer the file.
Most of the File Transport Window is self-explanatory but here are a couple of pointers: 1. Should the remote user use a different protocol than you, BCOM will usually detect this and report it on the "Last Message" line. 2. ERROR DETECTION type is either CRC or CHECKSUM, CRC is a preferred whereas CHECKSUM is inferior (EC modem users need not worry either way). BCOM will always attempt to use CRC if possible (except KERMIT). 3. The ERRORS CORRECTED section will update every time BCOM is requested to re-send a block of data.
BCOM has a BCOM TALK (Copyright ⌐ 1989-1993 BCOM COMPUTER) edit box. This allows all BCOM users (in all file transfer protocols but ASCII/BINARY) to chat with other BCOM users while send and receive file transfer is in progress. Another BCOM extra!
Simply type a message into the talk edit box and press the SEND MESSAGE button while the transfer is underway. When the remote user receives your message, the local edit box will empty, allowing you to generate more messages. When the remote user sends a message, it will be placed besides the bottom section labeled "REMOTE:".
To quit a file transfer, use the CANCEL button in the transport dialog BOX. It may be necessary to hit this button more than once if the remote computer is hung or the communications line has taken a severe hit. Please be patient if file transfer is aborted, BCOM will try to close down the session orderly. It may appear that file transfer is complete except it's waiting for acknowledgement from remote user.
C You may DRAG and DROP files(limited to how much memory is available) directly into the SEND BUTTON on the toolbar! If you need to send an entire directory it may be faster to enter a file specification using wildcards like *.*, *.??x, etc.
Should you experience trouble transferring files using BCOM QUEFILE, see the section labeled "File Transfer Errors".
Receive File(s)
Receive file(s) from remote users. Receiving files essentially is the same process as sending with the exception that most protocols require no file name be entered. XMODEM and ASCII/BINARY are the only exceptions. TECHNICAL NOTE: When using ASCII/BINARY or XMODEM and using BCOM-to-BCOM transfers, BCOM will automatically revert to the send side file name and file size once underway. Now that's the BCOM difference!
* * * * * * * * * * * *
If you have questions as to which protocol to use,
read the BCOM file transfer protocols explained section!
YMODEM BATCH, YMODEM-G BATCH, and KERMIT do not require a file name to be input. The received file name is automatically handled by BCOM and files will NEVER be overwritten. BCOM uses an automatic renaming convention ( COLLISION CIRCUITRY )for files that exist by placing a '$' in each character position (left to right) in the name until a unique name can be resolved.
For example:
A file in the host/download directory has the name "JUNK.TXT" and BCOM is receiving a file called "JUNK.TXT". BCOM will recognize "JUNK.TXT" exists and rename the new file "$UNK.TXT" ...and so on until the file was named ($$$$$$$$). In the event the same file name was received into the host\download directory more than 8 times (thus the file name reaches 8 '$" characters "$$$$$$$$"), BCOM could no longer receive the file. This will result in BCOM rejecting the file transfer and will be noted in the FTW LAST MESSAGE line. If this should happen, it will be necessary for you to manually clean-up the host\download directory and delete un-necessary files!
D When using ASCII and XMODEM, a filename will always be requested (even if using BCOM on the remote side; this is because the receiving BCOM cannot know in advance if a BCOM is sending). If BCOM happens to be on the remote side it will do automatic re-naming. BCOM will confirm file overwrites using XMODEM and ASCII/BINARY.
G A quick note about the File Transport Window (FTW Figure 5) and receiving files. There are many implementations of file transfer protocols (some better than others). BCOM expects the remote protocol to send information like the file size etc. but is not mandatory from the protocols perspective. Should the remote protocol not send this information, certain features on the FTW will be disabled (for instance, the % complete bar, file size and estimated complete time which all require a file size in advance for calculations). Disabling FTW features will not affect the file transfer itself, only the ability to monitor the progress of the file transferring!
G To quit file transfer hit the CANCEL button! Please be patient if file transfer is aborted, BCOM will try to close down the session orderly. It may appear that file transfer is complete except it's waiting for acknowledgement from remote user. If a quicker exit is desired the user may depress the CANCEL button a second time.
Should you experience trouble transferring files using BCOM QUEFILE, see the section labeled "File Transfer Errors".
Launch Fax Mgr.
Launches BCOM QUEFAX FAXMGR.EXE. Once the fax manager is launched, you may proceed with fax send requests and look to see if faxes have been received. For more information on BCOM QUEFAX see the BCOM QUEFAX Supplement Guide.
Fax Receive Now
This allows you to receive a fax now. Otherwise, BCOM QUEFILE normally receives faxes from host mode. Once the receive is successful, you may launch the fax manager and view the fax. For more information on BCOM QUEFAX see the BCOM QUEFAX Supplement Guide.
Capture File
Once invoked, BCOM will allow you to enter a capture file name where you can capture all sent and received characters. This is terminated when this feature is selected again, and the file is closed. The Capture File menu item will be checked to denote that it is currently selected. Performing a file transfer or leaving the package will also result in the capture file being closed automatically.
G If "ANSI Emulation" is enabled under the Terminal pull-down, ANSI escape sequences will not show up in the capture file. If you want to capture ANSI screens such as BBS logon screens, you must toggle "ANSI Emulation" to DISABLED while using Capture File. When you have captured the ANSI data you want, you may turn off the Capture File and toggle "ANSI Emulation" back to ENABLED.
C If BCOM attempts to open a existing capture file for write access, BCOM will first confirm if it is alright to overwrite the existing file.
Exit
The exit option allows the user to quit BCOM QUEFILE and go back to Windows.
Dial Directory Pull-down
Dial Directory
There are three primary functions that you may accomplish from this panel, 1. Select a dial entry and auto-dial them, 2. Tag a note to a selected dial entry, or 3. Edit the selected dial entry information and modem characteristics. Further, the dial dialog box is split into two sides, the left side is the DIAL and SELECT and the right side is for EDIT ENTRY.
1. AUTODIAL A DIAL ENTRY:
By selecting a dial entry from the dial entry listbox( either by mouse or UP/DOWN ARROW keystroke ), you may then click the DIAL button to dial that entry ( if one exists, if not see ENTER/EDIT A DIAL ENTRY later ).
BCOM will then exit this dialog box back to the main canvas and proceed to auto- dial( over and over ) until a connection is established. You may abort the auto- dialer at any time by hitting any pressing a key on the keyboard before a connection is made.
2. TAG A NOTE TO A SELECTED DIAL ENTRY:
The NOTE button allows users to tag a notes (text) file to the currently selected dial entry. First select the dial entry from the dial entry listbox on the left, then depress the NOTE button. The Notepad.exe application is called and BCOM QUEFILE places this line in each text file opened:
This file can be used to supply information about the dial entry like a password, user information, reminders, etc. When your edit session with Notepad.exe is complete, simply close the Notepad.exe application and save the file if desired. BCOM QUEFILE has predefined names for the notes files, BCOMWINx.N??, where x is the BCOM QUEFILE instance and ?? is the dial offset from 00-99.
3. ENTER/EDIT A DIAL ENTRY:
By clicking on an entry from the dial entry listbox on the left side, BCOM will automatically load the entry side (right) with its related information ( baud, parity, etc. ). You may edit these values to match those of the remote users computer. Once completed click on the UPDATE button to make changes valid for this entry.
G If you click on QUIT or DIAL without clicking on UPDATE, BCOM will not save these edited entry values. The UPDATE button actually tells BCOM to update the BCOMWINx.DAT file on disk when the dial dialog box is closed either by the DIAL or QUIT button.
Additional dial information...
The number entered in the "dial number" edit section is automatically prefixed by an "AT" generated from BCOM. This is a HAYES modem standard string for ATtention. Also prefixing the dial number is either the DialSuppStr 1 or 2 (see Configure/Set Strings). In (Figure 6) above, "Dsup2" represents the DialSuppStr2 radio button.
If it selected (darkened), the string has been selected, else DialSuppStr1 is used by default. The DialSuppStr2 radio button allows user to choose between the Supplement Dial String 1 & 2 under the Configure pull-down Set Strings option. This may be necessary for MNP and NON-MNP user init strings etc. Both DialSuppStr1 and 2 default to the "DT" string. Either DialSupp 1 or 2 are inserted after the "AT" and before the dial number. If outgoing calls require additional "AT" commands, central office switch commands, or call waiting disable/progress (*#9, etc ) keys, they may be entered here as well.
C You may perform an alpha-numeric quick sort on the dial directory entries by using the SORT button (If you want to save changes press the UPDATE button when done). The DEL button allows you to delete the currently selected dial entry (again, press the UPDATE button to save changes).
The BBS radio button is selected to tell BCOM that this dial entry is a BBS and can be included in the BBS rotary dial pool when the Dial pull-down BBS Dialer option is invoked (see the BBS Dialer below).
BBS Dialer
The BCOM BBS Dialer is a great for trying to connect with any one of your favorite BBS computer nodes during the busy prime-time hours. By selecting the BBS radio button for a dial entry from the dial directory dialog box, that entry now becomes eligible for rotary dialing from the BBS Dialer. BCOM starts with the first entry available from the selected dial directory entries, dials and waits for a connect string.
If BUSY or NO CONNECTION is returned from the modem, BCOM simply goes to the next BBS entry. This process continues and wraps back to the beginning entry until a connect is received. Once a connect is received, BCOM automatically drops the BBS Dialer and stays connected. If you have terminal connect beeps option turned ON, BCOM will continue to beep notifying you of the connect. Simply hit any key to stop the beeps. You may abort the BBS Dialer at any time by pressing any key on the keyboard before a connection is made during the dial process.
Notify Beeps
If you have terminal connect beeps option turned ON, once a Dial Directory or BBS Dialer connection has been established, BCOM will continue to beep notifying you of the connection. Simply hit any key to stop the beeps. If you are using an Audio Board or Multi-Media sound adaptor, you can edit or replace the BCOMBEEP.WAV file.
G Notify beeps are also used when using the "Dial" command within BCOM QUEFILE scripts.
( This page intentionally left blank )
Configure Pull-down
Com Ports
The CONFIGURE COM PORTS dialog box allows the user to configure the com port characteristics in order to talk to your modem properly.
G In order to communicate to another computer, these values must match the remote computers exactly!
G Once configured, use the "Save Config" option under the configure pull-down. This saves this configuration to disk and BCOM QUEFILE will use these values upon initial start-up.
G Remember, any dial directory configurations that are subsequently selected and dialed, override the start-up configuration.
The CANCEL push-button will exit com port configuration and will not re-configure BCOM.
The modem support listbox has been added to aid users in quickly setting-up BCOM QUEFILE modem initialization and reset strings to your particular modem.
G If your modem is not available, select one of the generic Hayes compatible modems. The modem support selection will automatically establish your modems MNP capability, reset and initialization strings. You may also fill in the modem initialization, and modem reset strings manually under CONFIGURE, Set Strings.
Also, for your information, most computers use 8 data bits, 1 stop bit and parity set to none.
Find Your Modem Port
This feature allows the user to have BCOM find what COM port your modem is connected to, then saves your configuration if successful. By sending the "ATZ" reset command, BCOM expects to find an "OK" from a valid port COM1-COM4. NOTE: If you have more than one modem BCOM will only find the first modem then quit.
Flow Control
Flow control of data can be equated to controlling water through a funnel.
D Without proper flow control it is possible to overrun your communication port and inflict COM PORT DATA READ/WRITE ERRORS resulting in LOSS OF DATA!
G Flow control option is absolutely necessary for BCOM users with error correcting modems (MNP/V.32) using high speed lines. This is particularly true when line speeds are set higher than the carrier speed (E.G. CARRIER 19200 CONNECT 34800). Flow control must be set to hardware (CTS/RTS) handshaking in order for proper operation of buffering data with high line speeds. See Appendix on ERROR CORRECTING MODEMS. Software flow control works fine for most low speed, text oriented data flow operations. If selecting software flow control, remember, you cannot transfer BINARY files because (0x13/0x11, AKA ctrl-S/ctrl-Q, AKA DC3/1, AKA XON/XOFF) characters will be stripped by the communications layers.
Modem Connect Type
The default connection type is MODEM, where BCOM expects that you are using a modem. A NULL-MODEM connection is helpful for users not requiring a modem. When using this and various BCOM functions, BCOM will bypass waiting on modem resets and certain other input. The MODEM connection should be used for most typical applications of BCOM QUEFILE.
DTR or +++ Reset
This option toggles between DTR transition and "+++" string OFF-LINE options. An off-line state is necessary when connected to another computer before the modem is reset. DTR or "+++" take your modem off-line and allows your modem to accept AT commands even when still connected to a remote modem. Most new modems support "&D2" for DTR transition to move the user offline and hang-up before reset. The DTR transition is faster than "+++" strings which must be sent during a timing window. If you cannot use the DTR transition use "+++".
Set Strings
A dialog box will appear containing a set of BCOM strings.
G Though individual edit boxes only show around 24 characters, they can contain up to 80. Use your mouse to select and your left and right arrow keys to move the edit cursor.
o Modem Initialization String
This string is responsible for initializing your modem. BCOM actually only invokes this string during BCOM QUEFILE initial start-up and host mode initialization. Most modems allow you to store init strings in the modems CMOS memory. BCOM will allow you to manually invoke this string from the SESSION pull- down. BCOM derives this from the MODEM SUPPORT listbox selection under COM PORT initialization.
o Modem Reset String
Most modems use the "ATZ" string to reset. Some have multiple setup profiles that allow a "ATZ0" or "ATZ1" to make that profile current. This string once sent to modem, actually does a hardware reset on the modem. BCOM allows this string to be sent manually under the SESSION pull-down and host mode also uses it. BCOM derives this from the MODEM SUPPORT listbox selection under COM PORT initialization.
o Modem Connect String
Once dialed to another user, BCOM waits for the modems to connect. This string is what BCOM expects to receive from the modem a valid connection. Reserved invalid connections are BUSY, ERROR, and NO_ cause BCOM to hang-up and retry. The connect string default is "CONNECT", which is available on most every modem with extended verbose codes from "ATX1" or greater. Other than the above invalid strings, the connect string only need be located somewhere in a carriage line terminated line. For example, with a configured connect string of "CONNECT" <default>, and with received data from modem of:
CONNECT 9600<cr> or 9600 CONNECT<cr> is OK, valid connect
but
NO CONNECT<cr> or just CONNECT with no <cr> is NOT OK.
o Host Initialization String
This should be used to invoke your modem into auto-answer mode (usually ATS0=1). When using BCOM Host Mode, BCOM sends this string after modem resets so the host may return to auto-answer mode. The Host Initialization String is really used as auto-answer string and can be manually sent to the modem under the SESSION pull- down.
o Primary Host Password String
G This string may be used for BCOM Host Mode but is primarily for when remote BCOM QueFiles are attempting login to your Host Mode. BCOM Host Mode verifies this string to allow access to top level Host Mode only ( for more information on Host Mode, see SESSION, Host Mode ). The user may not access DOS, change directories, or delete files. Remote QueFile users must have your Primary Host Password String in order for their QueFile request to be valid.
o Primary Host Password for DOS cmds
By design, this is to be used by QueFile in future implementations of BCOM QUEFILE to invoke DOS level work. You can currently use to gain entrance to your host mode Extended Dos Commands. This string if properly entered by remote user, allows access to sensitive DOS commands:
1. Change directory!
2. Delete files!
3. All other Host Mode DOS commands.
G BE CAREFUL WHO YOU GIVE THIS PASSWORD. You may need to change
it periodically.
o Host/Download Directory
When BCOM enters Host Mode or Receives files from other computers, BCOM places files/transactions into this directory. Remote users using Host Mode are only allowed to view, send, and receive to this directory without having the Host DOS Password. If installing BCOM from INSTALL.EXE BCOM defaults this to .\HOST.
o Supplement Dial String 1
This is the default string inserted before dial number out from the BCOM dial dialog box. It is intended to supplement the dial number as to GROUP types of numbers with a common string like:
AT command Group
9, to dial outside from PBX
DP dial using pulse
&Q5 use Error Correcting Dial string etc.
Here is how the dial string is built:
"AT"..................... provided by BCOM
"Dial supp 1 or 2"....... provided by DialSuppStr1 or 2 string
"DialNumber"............. provided by dial directory number
AT + DialSuppStr 1 or 2 + DialNumber > sent to the modem
It is up to you to configure group string 1 or 2 as you see fit.
o Supplement Dial String 2
Additional supplement string. See Supplement Dial String 1.
o Security Password
BCOM QUEFILE security password. Not currently available.
o Reserved 1
Character format reserved to save BCOM menu toggle functions.
G DO NOT ATTEMPT to change this string. BCOM changes this while updating menu item toggle features within the package.
o Xfer Char MaxWait Timeout
This is the MAX time in seconds that BCOM will wait for a character during file transfer. On very slow computers with slow connections and multi-tasking operating systems such as Windows, it is sometimes possible to actually timeout waiting for characters during file transfer. By raising this number, you can fix this problem. This value should not need to be modified.
o Fax Initialization String
Parameters required for BCOM QUEFAX to initialize the modem before sending or receiving a fax.
Quick View
Allows the user to see all the toggle features of BCOM. Toggle features are configuration menu options such as Flow Control. This is very helpful since toggle features are spread out over pull-down menus and each menu must be viewed in order to see all the toggle items and related check-marks. Select this option and BCOM places a printout information onto the terminal canvas.
Beeps and .Wav support
Allow/disallow the terminal to beep or use .WAV support at all times. Now BCOM has .WAV support. for 3 events:
1. BCOMBEEP.WAV Beeps ( beep required to terminal )
2. BCOMALRT.WAV Alert ( states: file transfer is complete )
3. BCOMISUP.WAV ( BCOM QUEFILE main didi )
C If you don't like the sounds delete them or better yet, record new ones using the same .WAV file names.
Host Users
A dialog box allows user to specify multiple ( up to 100 ) additional host users. There are two fields required for each user, the users name, password and optionally a DOS password. This is in addition to the primary password and primary DOS password under Set Strings. A file called BCOMWINx.PSW keeps these in text form. The user may edit this file. File format is:
user;password;DOS password
( Semi-colon delimited ).
It is only necessary to give most users access to only the password field. If you give a user the DOS password they may execute extended DOS commands: CD, RD, MD, DEL, TYPE and COPY.
G BE CAREFUL WHOM YOU ALLOW THIS LEVEL OF ACCESS!
All users other than DOS level users are restricted to using the host/download directory on your DISK.
To update the user file just enter the information on the panel and press OK. This will write the BCOMWINx.PSW file. If you select CANCEL it will abort the update.
Security
Not Currently installed.
Toolbar
BCOM now introduces a toolbar that allows you to perform the most commonly used functions faster. There are currently 9 buttons:
...RESET allows you to disconnect quickly by invoking your reset modem options here.
...HOST Allows user to invoke BCOM QUEFILE Host Mode.
...DIAL Gives you the dial dialog box with a single click.
...SAVE Allows user to save BCOM QUEFILE configuration, menu options and screen position.
...SEND Allows user to enter send file(s). You may also Drag and Drop files to the send button.
...RECEIVE Allows quick access to receive file transfer.
...CAPTURE file characters sent to and from the com port.
...SCRIPT allows you to launch scripts from a button.
...QUEUE files to a remote BCOM QUEFILE user in host mode.
You may send files to remote users by using the BCOM DRAG and DROP feature. Files can be dragged and dropped into the SEND button on the toolbar! If you need to send an entire directory, it may be faster to use wildcard specifications like "*.*". A quick reminder, The toolbar may be called "button bar" in some areas of this document.
Save Configuration
Save ALL BCOM QUEFILE configuration information to disk in the BCOMWINx.CFG file. All menu toggle items and screen position information are saved!
G BCOM QUEFILE will never save configure information unless the user has requested it.
Session Pull-down
Modem Init String
Send the modem initialization string to the modem.
This string is set in Set Strings under configuration pull-down.
Modem Reset String
Send the modem reset string to the modem.
This string is set in Set Strings under configuration pull-down.
Host Mode
Provides unattended remote access to your computer. Configured remote users may either dial up your Host Mode and use the menus provided or use their BCOM QUEFILE to QueFiles to your Host Mode. Select Host Mode which will queue a Host Mode event. As soon as BCOM can free up other events it will reset modem and say "BCOM Host Mode reset and ready!". At this point authorized remote users may dial into your system. In order for them to gain access to your system they must first have you issue them a userid and password from the "Host Users" setup under CONFIGURE.
The remote user will be presented a BCOM Host Mode command menu to choose from:
Host command menu.
For example, a remote user can elect to have your Host Mode send them a file. The remote user would first select the transfer protocol "f ?" and type the appropriate '?' letter (ymodem default) from a BCOM Host Mode supplied protocols menu (not shown). Then, type "s filespec". If BCOM can find the file, it will say "GET READY FOR FILE XFER". If the file is not found it will report the problem to the remote user. The remote BCOM Host Mode user can ALWAYS type "DIR", and BCOM Host Mode will display the Host/Download directory to them. If the user has successfully answered the DOS password, the user may select a new directory other than the Host/Download Directory by using the "CD" command, like "CD .."
NOTE: By design, this limits host users without the DOS shell password to only the Host/Download directory for security.
Host commands menu explained:
c)hat
Allows the remote user to page/request
conversation with the local BCOM operator( if its not
un-attended ). BCOM host mode
will beep 10 times ( 1 time per second ).
If BCOM Host Mode is attended ( your home ), you
may chat with the remote user by simply hitting any
key ( other than ESCape ).
The remote user will be informed
"OPERATOR ON-LINE". Full duplex conversation may
continue until the operator hits the ESCape key to
place the remote user back into normal host
mode session.
C The local BCOM operator may type messages to the
remote user any time the host mode is displaying the
normal canvas (E.G. not while file transfer is
going on). Hit any key (but escape) to chat.
g)oodbye
Results in termination of the remote user from the
current host mode session. The session will attempt
to DTR/+++ off-line, then reset the modem. After this,
host mode will attempt to re-initialize the modem
and send the host initialization string. BCOM will then
be ready to accept more users.
s)end file
Allows remote user to send file(s) from BCOM host mode
PC to their PC. The user must select which file to
send. E.G. "s junk.exe"
If the file is available, host mode will tell the
remote user, "GET READY FOR FILE XFER". HINT: user
must select the correct protocol by using the "f"
menu option first. Also, if the user needs to see
which file is available for transfer they may type
DIR. If they have a DOS password they may enter other
directories other than the host/download directory.
l)eave file
Allows a remote user to leave file(s) on the local
BCOM host PC. Leave file requires the user to specify
a filename in case the protocol does not send a
file header with an embedded file name. See HINT area
in the Send File section for more tips.
f)ile transfer protocol
Allows remote user to select between BCOM file
transfer protocols.
m)essage
Allows user to leave a message to the local BCOM host
operator. Once selected, the remote user is given the
opportunity to type a message and ESCape to quit
and save. Each message is left incrementing order.
They are placed into the host/download
directory with a name of BCOMWINx.nnn (where nnn is
a decimal number from 000-999), thus 999 possible
messages. BCOMWINx.MSG file contains the highest
message number 000-9999 to date and may be
manually reset using any text editor.
The saved message on disk will be prefixed by the
users name who left the message along
with the date and time it was saved.
Example message: BCOMWIN1.N03 (third message to date)
The BCOM Host Mode DOS sections below uses normal DOS syntax for their respective DOS commands.
DOS commands available to all:
DIR - Currently only the DIR command is available. This
allows all users to get directory information of the
current working directory ( host/download ).
Extended DOS if authorized: ( requires DOS password )
CD - change directory: cd .., cd b:\tst, cd test etc.
RD - remove directory: rd \junk, rd tst
MD - make directory: md \tst, md c:\hiya
DEL - delete file(s): del *.*, del tst, del c:\hiya\*.tst
BCOM supports a "BCOMWIN[x].psw" (where [x] is the instance 0..9 etc.) file for multi-user host support. To enter additional users see CONFIGURE Host Users. BCOM allows a list of users in this format:
user;password;DOSpassword
user;password;DOSpassword etc.
User id, password, and DOS password must be ';' delimited. Each line should end with a Carriage Return. User ID's should be unique or the first instance will be assumed.
G If you don't wish to maintain a multi-user Host Mode, you may simply maintain only the primary password and DOS password string under configuration "Set Strings". Passwords are the only case sensitive strings in Host Mode. All input in Host Mode is carriage return terminated.
C If the Host Mode connection becomes inactive (no typing, no file transfer) for over 2 minutes, BCOM Host Mode will first tell the user "IDLE TIMEOUT EXCEEDED", then attempt to reset and re-initialize the connection. This will stop people from logging in and forgetting to logout of Host Mode.
More on Host Mode...
To display a custom banner to users after a user has logged in,
place a ascii file called BCOMWINx.HST in your host/download directory. Of course the x in BCOMWINx stands for the instance of BCOM in use. An example .HST has been supplied in the BCOM QUEFILE install directory. This file can be as long as you want but place a 'ctrl-l' character in the first column of any place you would like the banner to pause and make the user hit a key to continue. A 'ctrl-l' any other place than column 1 results in a form feed to the remote user. The maximum line length supported in a .HST file is 255 characters.
G Host mode may be entered automatically upon Windows start-up if you do the following:
1. Place a copy of BCOM QUEFILE into the PROGRAM MANAGER StartUp GROUP (this is Windows equivalent to the DOS autoexec.bat file).
Please refer to your Microsoft Windows manual for more information on the Windows program manager StartUp group.
2. Using the FILE option of Program Manager, select Properties.
Add these command line arguments:
\WINDOWS\BCOMDIR\BCOMWIN.EXE 0 /h
The '0' (zero) argument is the instance and the '/h' tells
BCOM to enter host mode upon execution.
G When using the TyIn 2000 use "/htyin" which bypasses normal
host init proceedures and places the remote user directly at
the host prompt. Also, when the user attempts to logoff,
BCOM will close the BCOM application so that it may be invoked
on the next data phone call.
G Users may want to enter BCOM QUEFILE Host Mode when your computer is powered on.
1. Place "WIN" in your autoexec.bat file ( if necessary ).
2. Follow the steps above to place a copy of BCOM QUEFILE
in your program manager startup group.
Description: Your computer should power-up and execute its autoexec.bat where WIN will load Windows. The Windows StartUp group item, BCOM QUEFILE, will use the "/h" option and load BCOM QUEFILE into Host Mode.
To exit host mode, press the ESCape key while host mode session is at the canvas level.
G Be careful, you can exit host mode even while a user is logged on. BCOM will confirm the exit of Host Mode!
Auto-Answer String
Send the Host initialization string to the modem. This string should be configured to place you modem into auto-answer. Usually set to ATS0=x. The x specifies what ring count in which the modem should auto-answer the phone call ( usually 1 ).
D If x is set to zero, you state the modem should not answer the phone call thus disabling host mode.
A FAST 19200:N,8,1
Fast configure option for Baud rate of 19200, No parity, 8 data bits and 1 stop bit on the current port in use.
G If your computer/modem is not using a 16550 high performance serial port, Windows communications will be unstable.
B FAST 19200:E,7,1
Fast configure option for Baud rate of 19200, Even parity, 7 data bits and 1 stop bit on the current port in use.
G If your computer/modem is not using a 16550 high performance serial port, Windows communications will be unstable.
C FAST 9600:N,8,1
Fast configure option for Baud rate of 9600, No parity, 8 data bits and 1 stop bit on the current port in use.
D FAST 9600:E,7,1
Fast configure option for Baud rate of 9600, Even parity, 7 data bits and 1 stop bit on the current port in use.
Script
A Dialog box will appear which allows you to enter a BCOM script file name that usually has a ".BCM" file extension. Use the List Files of Type filter (bottom left) to sort only .BCM files.
Script files(.BCM) are basically ASCII text files using a predefined set of BCOM script commands to automate redundant chores like logging into other computers and lots more. You may enter host mode, send/receive files, dial users from the dial directory, and more , see the commands listed below.
Once you have entered a BCOM script file name select "OK" to run it or "CANCEL" to quit. You may edit script files with your own text editor. Several ".BCM" files are provided as examples. The easiest way to prepare logon/logoff scripts is to capture the initial session with FILE/CAPTURE FILE then cut and paste it with your editor into BCOM script commands (below). You may also want to use the clipboard facility with the Windows Notepad.
Script commands:
BAUD <rate 300-256000>.
DELAY <XXX> in half seconds, XXX is an integer < 32,767
half-seconds/ five hours.
CLEAR screen.
COMMENT <use for a comment, does not get executed or printed>.
DIAL <XX> a number from the BCOM dial directory. Uses
associated setup BAUD/ETC. information and auto-redials
until a connect.
DO_NEXT_IF <string> matches INPUT text, next script line
will execute. This is great for decision making. Example:
<gets line of text from remote computer>
DO_NEXT_IF NO CONNECT
RESTART
EXIT exits the BCOM QUEFILE scriptor.
HOST allows the user to enter host mode from the script.
INPUT <string> from modem, use with DO_NEXT_IF and REMOTE from INPUT, will wait for characters at hard coded timeout of 25 seconds. Timeout, carriage return or linefeed terminates input.
KBHIT wait for keyhit from keyboard.
PARITY <X> use a 1 or 0, 0=8bits No Parity & 1=7bits Even Parity.
RESET use bcom disconnect option and reset modem.
PRINT <comment to screen>.
REMOTE also see XFER, allows a remote user to enter
"XFER R Y FILESPEC" string to execute file transfer.
RESTART begin back at start of script file.
SCHAR <X> send single character X to modem.
SEND <message to modem>, followed by <cr> after SEND = <cr>
only sent.
SLEEP <XXXXXXXX> seconds to next event, X's is a long
integer < 4000000000 seconds or ~= 740 days or 2 years
worth ( 86,400 seconds in a day ).
TIME <08:20:00> padded military time, waits until 8:20 am
to continue with next script event.
WAIT <XX> <SSSS> where XX is time in seconds to wait for
SSSS string.
XX=00 directs BCOM to wait for SSSS string forever.
Script Commands Continued...
XFER <M> <T> <FILESPEC> - transfer files using BCOM file transport.
Also see REMOTE. Arguments: <FILESPEC> like *.*
or filename.ext.
<M> = mode S|R send/recv,
<T> = type xfer X = XMODEM
Y = YMODEM BATCH
G = YMODEM-G BATCH
A = ASCII/BINARY
K = KERMIT
This uses the current working directory.
G Hit a key at any time during script to abort (except when using KBHIT verb).
Offline + ResetModem
A DTR transition or "+++" offline and reset string followed by the Modem Reset String are sent to the modem. An "OK" is expected back ( for both strings if using +++, else reset string) to get a BCOM MESSAGE: BCOM reset successful. Else, unsuccessful. See also, DTR/+++ Reset under the Configuration pull-down.
Terminal Pull-down
ANSI Emulation
This should be enabled if you intend to see ANSI color or draw ANSI GRAPHICS.
D If DISABLED, BCOM can no longer interpret ANSI ESCAPE SEQUENCES which enable color, screen addressing, etc.
You may elect to set ANSI Emulation to DISABLED when using the capture file to grab ANSI screen data (like line draw, graphics, etc). Escape sequences are reserved character sequences that format data displayed to a terminal. For more information on ANSI escape sequences refer to your DOS Users Guide, ANSI.SYS.
Optional Emulators
This option is not currently installed.
Echo
The default is no echo, which indicates the remote computer must echo back characters you type in order for you to see them. Most host computer's do this, but when chatting with friends from computer to computer you'll want to turn ECHO on, so you can see what your typing!
G If echo is set incorrectly you will experience one of these symptoms:
1. No echoed characters when you type.
2. Double typed characters(HELLO would appear as HHEELLLLOO).
CRLF/LF
Carriage return/Line Feed expansion On or OFF. When OFF (default), Carriage returns received from a remote user do not scroll your screen. This is because when attached to remote computer Hosts, they offer Line Feeds with Carriage returns that do scroll your screen. Like ECHO, turn this on when talking to someone's computer that is not in a Host mode. When talking to a host type computer turn off else you'll get double line feeds.
Color
BCOM has full terminal ANSI color support. Unlike other packages, BCOM is FULL size screen and font. This makes BCOM come alive when talking to remote computers like BBS's. BCOM incorporates as much of the ANSI full screen implementation that was possible(in a window). Because of the quirky behavior of absolute screen addressing in a window, BCOM implements these features in this way:
1. Scroll up/down fully supported. Wrap around automatic.
2. Stock OEM Font - Lines per screen and characters per line are
determined by the screen size vs. character size.
True Type Font always contains 24 x 80 characters on
the screen.
3. Line feeds are only next line destructive if cursor line
was equal to the last screen line when received.
4. Screen array is 100 x 80 x 16 color support
( dynamically allocated ). Thus up to a 100 line window
could be supported when using the Stock OEM Font.
Colors have been pre-selected to emulate that of 16 color DOS packages. When color is DISABLED, the screen wil be set to a default of black characters on a white background.
TTF/OEM Stock Font
The user may select either True Type OEM embedded font, or the Windows OEM Stock font. True Type is scalable and allows the user to scale the font to the current physical window size (thus BCOM makes it TTFRowsOnScreen{25 default rows} x 80 columns).
D It is possible that certain screen size variations may produce an undesired character aspect ratio. This will sometimes (rarely) result in screen character misalignment and offset, or cursor-to-character tracking problems.
C To avoid this, try one of these:
1. Re-size the screen slightly.
2. Try using the TTFRowsOnScreen or SnapHeightTo24 option.
3. Try using the OEM Stock font instead.
G The OEM Stock font is a fixed pitch font that is not scalable. This may be desired when you wish to have more or less than 24 lines viewed.
TTFRowsOnScreen
Applies only when the TTF font is selected, otherwise it is grayed out. A combination edit/listbox is presented that allows the user to enter the number of rows (3-99) that will be used as the display line height. The TTF font size will automatically adjust the display grid made of 80 columns wide by the TTFRowsOnScreen. You may have an occasional need to change this value but, typically it should be left at the default 25 rows!
G See the section under SnapHeightTo24 that explains screen size mismatches.
SnapHeightTo24
Applies to both the TTF and OEM Stock fonts. SnapHeightTo24 allows you to quickly snap the screen row height to standard 24 line display.
G It is especially important to have 24 line display when connected to an remote host that expects you to be using a 24 line display. This is especially true when using ANSI interaction (requiring use of arrow keys: left, right, up, down). For example, a menu allows you to TAG files. BCOM utilizes a 100 line wrap buffer in which the physical canvas is a viewport.
D Screen size mismatches can cause problems when the remote computer expects the screen height to be 24 lines. You should either use the True Type Font, SnapHeightTo24, or use a larger screen in which case you should configure the remote computer to accept your larger or smaller screen size.
Copy Area to Clipboard
If enabled, the user may select a rectangle of text from the BCOM QUEFILE main canvas and copy it to the Windows clipboard. BCOM will mark the text rectangle in reverse video. To select text from the canvas, first move the mouse to the desired area. Then, depress the left mouse button to start the selection process. Move the mouse right and downwards to make a rectangle of desired text ( in reverse video ). Now un-depress the left button and BCOM will prompt: "Copy text to clipboard?". If YES, the text will be sent to the clipboard for use with other applications that use the clipboard where it may be then pasted. If NO, the text in BCOM's buffer will be discarded.
G If disabled, BCOM will no longer monitor the canvas for mouse and button movement.
Paste Clipboard to Port
If enabled (not grayed out), the clipboard has compatible (TEXT or OEMTEXT) data that has been cut or copied to the clipboard. If you select this menu item, BCOM will send this data directly to the configured communications port.
C This is great for users who want to annotate files with notes to each other or send pieces of files quickly (without having to save to files then send them!).
G BCOM does not echo the sent characters to the canvas. If the remote users package does not echo characters you may not see the characters being sent.
F1 Help/Sent
Upon the user hitting the F1 key on the keyboard, the F1 key is either:
1. Stripped and used by BCOM to call the BCOM QUEFILE ON-LINE
HELP FACILITY.
2. Sent to the com port ( in VT100 ESC format ).
Cursor Home/Clear
Clears the screen ( and all 100 lines in the circular buffer ) and homes cursor in upper left. This also occurs when the remote computer issues an ANSI escape sequence of "escape[H"
Clear Screen
Clears the screen ( up to 35 lines of canvas ).
QueFiles Pull-down
Schedule
QueFile allows you to schedule automated file transfer to and from other BCOM QUEFILE nodes any time day or night, 365 days a year. This is great for sending or receiving files to unattended BCOM PC's or your friends BCOM Host Mode in the middle of the night (when long distance rates are low). This allows unattended PC to unattended PC operations to be performed. All other communications packages make you use lengthy or hard to use scripts.
C BCOM has simplified complex scheduled file transfer to a single dialog screen, now its a snap!
G The only other requirement is that your remote friend (or PC) needs BCOM QUEFILE installed, and must be running in host mode to accept the QueFile request.
The scheduling dialog box is really four boxes in one. The top box is a listbox of queued files. The bottom left box has the direction send/receive selector and file name gathering controls. The bottom middle box is a listbox of your dial directory entry names. The bottom right box has controls for the month, day, hour, minute, and remote users password. All the bottom boxes configure the top box.
Start by clicking on an entry in QueFile queued file listbox (on the top box). This is where new QueFile information will go.
Now go to the "File Section" ( bottom left). The direction push-button specifies the file transfer direction, Send or Receive. If you want to send a file, click on an available file in the listbox or enter a filename in the filename edit box. If you would like to receive a file, you'll have to use the edit box because BCOM doesn't have a list of the files from the remote node. Also, the file if received must exist in the remote PC's BCOM QUEFILE host/download directory. Wildcards may be used in the filename edit box. If you desire to change the directory, simply enter a new path name in the top edit box and click on the refresh button. The default directory is the BCOM host/download directory.
Now a target dial directory name/entry from the dial directory listbox (bottom middle) is required. These target dial directory entries ( remote PC's ) must have BCOM QUEFILE running in Host Mode to allow this QueFile request to be successful. The bottom right box contains combination boxes (edit and list) that allow the user to select the month, day, hour and minute the file should be transferred. Also, the bottom right box contains the password edit box is the remote BCOM users primary password from their Configure Set Strings dialog box.
G In order for the QueFile transfer to complete successfully, this list must be completed:
1. Complete the scheduling box information correctly.
2. You must have the remote BCOM primary password (for
security reasons).
3. The remote PC must be running BCOM QUEFILE in host mode.
4. The remote BCOM package must have QueFile enabled, under
QueFile Enable/Disable.
G Now click on the "QUEUE" button. The entered information should now be represented in the upper (top)QueFile listbox. This entry is now queued and avilable for BCOM as soon as you "QUIT" button.
The Standard state of all entries is QUEUE. This means BCOM is polling (checking) for valid Day and time stamp to launch this operation. All QueFile entries have the date BCOM QUEFILE started up. BCOM QUEFILE matches the real date with the QUEUE date. If they are the same and the time matches or the time or date has already occurred for this DATE BCOM will launch the process. The process is on a thirty second queue so you will have approximately thirty seconds to hit delete and purge the process.
By clicking on the "RELEASE" push-button, you will effectively bring this QueFile entries time and date current, thus BCOM will try to execute once leaving this dialog box using the "QUIT" button. This is convenient when you want an immediate launch of an existing entry that has some future date and time already set.
C BCOM will never execute a QueFile while this dialog box is up, giving you a chance to change your mind and change or "DELETE" it. You may re-queue over a enqueued entry!
To launch a QUEFILE entry, the QueFile date must be less than or equal to the current date/time (month:day:hour:minute).
C BCOM is aware when a previous month, day, or time has expired and should launch expired QueFiles as soon as possible.
D The negative side to this is you cannot queue ahead to the next year! Jan 01 of 1995 would be less than Dec 25 1994 because BCOM does not currently watch the year. Once a date is matched however, BCOM can determine if the file time has expired for that DAY and execute any expired times for that day. For example, if the date/time was:
Jun 10 15:33
and your QueFile was date/time stamped:
Jun 10 11:22
BCOM would immediately start this entry.
HOWEVER, if the QueFile was date/time stamped:
Jun 10 15:35
you would have 2 minutes before the entry would launch.
Date: ( two combo-boxes supply all the correct entries )
Valid Recognized Months ( 3 char, CAP first letter ):
Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec.
Valid Recognized Days ( Zero Padded 01-09 ):
01, 02, 03, 04, 05, 06, 07, 08, 09, 10-31.
Time: ( two combo-boxes supply all the correct entries )
Valid Recognized Hour uses a 12 hour clock. For example 12am-
11:59pm. BCOM expects a 3 character string to represent
this. Example 12a = 12 am, 01a = 1 am and 11p = 11 pm.
Valid Recognized Minutes ( Zero Padded 00-09 ):
00, 01, 02, 03, 04, 05, 06, 07, 08, 09, 10-59.
BCOM internally translates 12 hour time to a military 24
hour clock:
1:00pm in the afternoon would be 13:00.
1:00am in the morning would be 01:00.
G You must now click on the "QUIT" button to execute the current QueFIle list. BCOM will notify you it is taking session control by saying "BCOM MESSAGE: BCOM QUEFILE IS TAKING SESSION CONTROL".
Once a QueFile is in progress, it will attempt to auto-dial ( over and over ) the tagged dial entry until a valid modem connection is established. If other QueFiles should be queued for execute ( even to the same target dial entry), they must wait, FIFO (first in match, first out) for the first one to finish ( ABORT or DONE! states).
The next event or QueFile will execute after the QueFile in progress is terminated. Once connected, BCOM QUEFILE will send a (encrypted for security) start command and your Send/Receive operation will be processed. If at this point your password matches their primary password, BCOM will do file transfer else it will abort the QueFile session and this will be indicated in your QueFile Dialog listbox.
BCOM QueFile requests will take session control away from the user. Should you experience trouble with your QueFile, use the List Queue(s) option under the Internal pull-down. This will indicate if a QueFile is underway but not under retry (30 seconds). Once a QueFile is underway and an error occurs, it will attempt to retry a total of 3 times. If your foreground session appears to be tied up ( non-responsive) and you want immediate control back either:
1. Clear Queue(s) under the Internal pull-down
(clears all queued events!).
2. Enter QueFile schedule and DELETE the entry, QUIT and wait
for the current retry to finish.
3. Exit and re-enter BCOM.
There are currently 3 possible states for QueFile entries:
QUEUE - valid, being checked.
ABORT - Either invalid ( NON-BCOM ) node at other end or
BCOM aborted transfer due to bad password.
DONE! - operation completed.
The "DELETE" push-button cancels the highlighted QueFile entry and deletes it from the dialog box. It clears out queue position and returns state to QUEUE.
G Though the QueFile process may sound complex, it is really quite easy. Try it with a friend, you'll really enjoy this feature!
Enable/Disable
You may want to disable remote users from using BCOM QueFile on your PC for security reasons. When disabled, remote users attempting to QueFile onto your PC results in an ABORT state on their PC QueFile entry. This provides an addition level of security for you. Remember, they must still have your password in order to get files from your disk. As well, they (BCOM QueFile) only have access to your Host/download directory.
Save Queue to disk
BCOM QUEFILE now allows the user to save ( dump ) the QueFile entries from memory to disk. When used in conjunction with "Get Queue from disk" or "AutoLoad Queue at start-up", allows the user to restore QueFile entries to their exact state when last saved.
Remember, the file data is not saved, just the scheduled entries. The significance of saving queued entries results in the ability to store and reload complex file transfer scheduling with the click of a mouse. BCOM QUEFILE uses a reserved file name BCOMWINx.QUE to hold the entire Queue on disk.
Get Queue from disk
Allows the manual invocation of retrieving saved QueFile entries from BCOMWINx.QUE. See also, Save Queue to disk above.
AutoLoad Queue at start-up
Allows the automatic retrieval of saved QueFile entries from BCOMWINx.QUE at BCOM QUEFILE start-up. Therefor, BCOM will automatically restore saved QueFile data from the previous BCOM QUEFILE session and continue on.
Also, if this option is selected, upon any change of any BCOM QueFile entry event status ( from QUEUE to DONE or ABORT), BCOM will automatically save the current queue in memory to disk. See also, Save Queue to disk above.
G This option effectively automates QueFile and will keep the queue current through computer power-downs and bringing BCOM up and down.
Protocol
Allows the user to specify which of the BCOM QUEFILE supported file transfer protocols to use for all QueFile initiated file transfers. If you wish to save this information, you must manually save this under "CONFIGURE Save Config" or use the toolbar Save Config button.
Internal Pull-down
Debug/Queue
Allows debug of specific BCOM functions, like character position,
character size, and more.
Clear Queue(s)
Clear events that have not occurred yet, but not in execution.
List Queue(s)
List the next available 15 events. EVENT# is the current event of 200 possible in queue. PTR# is where the next event will be placed.
Event........ The event queued,
INACTIVE, DIALING, HOST MODE, HOST ABORT,
QUEUE FILE, TRANSFER, BANNER
State........ State of event, 0 idle, -1 execute, else return code.
Description.. Of the event, additional information.
Help Pull-down
Index
Will take the user straight to Windows HELP and display the user BCOM QUEFILE HELP CONTENTS. All major topics will be displayed. Users may also access this by pressing F1 at any time during the BCOM QUEFILE session.
Using Help
G This option allows the user to get Help on how to use the Windows Help facilities. Users unfamiliar with Windows should review this before using BCOM's help facility.
About BCOM...
Program information about BCOM QUEFILE, including version number.
Shows ICON BCOM QUEFILE will assume when minimized.
BCOM file transfer protocols explained
XMODEM explained:
Packet size: 128 bytes.
File header info: Implemented. 128 byte header.
Filename, size.
Error Correction/
Detection: CRC 16, CHECKSUM
Files per transaction: Single.
Notes:
BCOM's version of XMODEM implements a robust implementation.
BCOM has been tested to over 40 different implementations.
High overhead, every 128 byte data packet is acknowledged,
1 to 1. Use XMODEM when nothing else is available.
YMODEM BATCH explained:
Packet size: 128/1024 bytes inter-mixed.
File header info: Implemented. 128 byte header.
Filename, size.
Error Correction/
Detection: CRC 16, CHECKSUM
Files per transaction: Multiple.
Notes:
BCOM's version of YMODEM implements a robust implementation.
BCOM has been tested to over 40 different implementations.
Lower overhead, every 128/1024 byte data packet acknowledged,
1 to 1. Use YMODEM over XMODEM but use G-YMODEM if you can.
YMODEM G-BATCH explained:
Packet size: 128/1024 bytes inter-mixed.
File header info: Implemented. 128 byte header.
Filename, size.
Error Correction/
Detection: CRC 16, CHECKSUM
Files per transaction: Multiple.
Notes:
BCOM's version of YMODEM-G implements a robust implementation.
BCOM has been tested to over 60 different implementations.
When using error correcting modems, this has the highest
performance. Use over all other protocols.
Lowest overhead, data packets assumed acknowledged unless
negative acknowledgement ( NAK) is received.
ASCII/BINARY explained:
Packet size: 1 byte
File header info: Implemented. 28 byte header.
Filename, size BCOM-BCOM only.
Error Correction/
Detection: None.
Files per transaction: Single, Multiple BCOM-BCOM.
Notes:
BCOM's version of ASCII/BINARY is straightforward.
- Configure capable MARK(SOH, 0x01),QUOTE(#,0x23) and
PREFIX(&,0x26) characters.
Somewhat high overhead, every data packets acknowledged 1 to 1
with a 5 byte response. Binary Data is prefixed sometimes
causing a 1 or 2 bytes overhead for every byte sent.
Use other protocols if you can.The KERMIT implementation
along with other BCOM supported protocols are to make
file transfer as simple as possible.
KERMIT was added to simply compliment other BCOM protocols
and provide additional connectivity to HOST type computers
or where other BCOM protocols were not supported.
File Transfer Errors
If executing file transfer and an error occurs, try the transfer again. If the failure persists, try another protocol. If that doesn't work try these :
1. Verify your modem is set up to use the correct
"AT" modem initialization parameters. If you have an
MNP error correcting modem, make sure you have implemented
all the proper commands. Many MNP style modems have an
"EC" or some light indicating they are in error
correcting mode. You can also tell by the ATX1-8
connection result if you are using V.32/ MNP / LAPM etc.
2. G If your using speeds above 2400, make sure you have
implemented hardware CTS/RTS end-to-end level flow control
on both modems. See Also: Error Correcting Modems section.
3. Verify you don't have an excessively noisy phone
connection. Line hits ( noise on phone line ) are the
number one killer of file transfers even with error
correcting modems. Call the remote PC back in 20 minutes
and see if you can transfer then. If you have call-waiting
try disabling it ( sometimes you can dial "*70"
or some code ).
4. Watch the BCOM TRANSPORT dialog box "LAST MESSAGE". It
usually is a real verbose indicator of what's wrong.
Error Correcting Modems
When using EC or MNP style modems, it is necessary to set the line speed between the computer ( via BCOM ) higher than your modem carrier can connect with. For example, a 2400 baud MNP style modem can usually have a line speed up to 9600 bps. This usually results in return codes of CARRIER 2400 with a CONNECT 9600. A 9600 MNP modem can run at 19.2Kbps or even 36Kbps. This is due to the fact that the modem can compress and buffer data. This often results in bursts of data to and from the PC. It is necessary to monitor and raise/lower hardware signals to prevent data overrun or even loss. Set your modem to monitor CTS/RTS signals for HARDWARE FLOW CONTROL. When using Error Correcting Modems, do the following:
1. Physically set up modem according to the modems
owners manual.
2. Use the DialSuppStr2 option in the dial directory for
MNP users. This way, NON-MNP users default to
DialSuppStr1. Place the setup string for your modem that
places it into Error Correct mode in:
a. CONFIGURE Pull-down
1. Set Strings
a. DialSuppStr2
3. G Set the baud rate as high as the modem/BCOM can handle.
NOTE: If you are using baud rates over 9600 it
is absolutely necessary that you install a 16550 high
performance FIFO port for your modem. These may
be usually purchased at any computer store.
4. Under CONFIGURE pull-down, set flow control to HARDWARE.
BCOM's Hardware flow implements CTS/RTS. Buffers are 10k.
5. Use the Ymodem-G protocol for EC or MNP modem transfers.
This protocol does minimal error checking, no wait for
end-to-end acknowledgements, the ability to cram
data into the modem faster than it can send thus has
high performance.
BCOM QUEFILE DDE Client/Server
BCOM QUEFILE now incorporates Dynamic Data Exchange or DDE. DDE enables BCOM QUEFILE to receive commands through the Windows DDE message queue. Developers may use the DDE1.exe and related code DDE1.C ( BCOM COMPUTER can make all .rc, .h, .def and etc. files available to authorized users ) to build an application that uses BCOM QUEFILE DDE commands. The DDE ( app, topic, and BCOM ) command set is documented in DDE1.C file.
G The DDE command set allows developers to hide and show BCOM ( LOCKUSEROUT / UNLOCKUSER), queue Host Mode(HOSTMODE), manipulate (get/save) the QueFile .QUE (GETQUEUE and SAVEQUEUE) and invoke any script file (SCRIPT_filename). Invoking QueFiles or script files gives developers the ability to send/receive files, schedule file transfers, dial other users, and lots more. For more information on script commands see the Session/Script section above.
G Developers may generate the script files or QueFiles then have BCOM QUEFILE launch them.
Glossary
ANSI - American National Standards Institute. ANSI escape sequences make screen formatting and multi color screens possible.
Application - A program such as BCOM QUEFILE, CLOCK, CONTROL PANEL.
ASCII file - usually files that contain only text.
Background - The area behind an active window.
Baud Rate - The rate in which bits of data travel from modem to modem.
Binary files - Files like (.exe and .com) files or text files with control characters from ctrl-a - ctrl-z.
Canvas - The main screen of a window.
Carrier - A tone from the modem which data is carried on.
Click - When you quickly press and release a mouse button.
Comm Port - see Serial Port.
CPS - Characters Per Second. Referring to how fast data can travel. A 2400 baud line divided by 8 bits per second results in a max of 300 characters per second. There is also a phrase BPS for Bits Per Second where there are 8 bits in a character.
Dialog Box - A special type of window that serves a particular purpose.
DDE Dynamic Data Exchange - A communications method Windows incorporates to allow applications to share information.
Drag and Drop - Allows users to tag a group of files and drag them to an application that will accept them where the user may then drop them.
ECM - Error Correcting Modem. A modem such as an MNP modem that is capable of detecting errors and retransmission of frames independently of the communication software package.
Filespec - A filename or specification like "file.txt", "*.exe" or "*.*".
Flat file - see ASCII file.
Icon - A graphical representation of an available resource, file, drive, application, etc.
Modem - A device that allows communications from one computer to another over phone lines.
MNP - An error correcting, compression protocol that allows the application such as BCOM QUEFILE to have a more reliable transfer layer.
Off-Line - When BCOM makes isolates communications between computer and modem.
On-Line - when BCOM makes communication available between computer and modem.
Path: DIR
Pathspec - A pathname and or drive. Like "c:\dos", "a:" or "\windows".
Protocol - X/Y/Zmodem, A predefined set of rules in which computers can transfer files and file information.
Scroll - To move text/cursor up, down, left or right.
Select - Click to highlight a entry.
Serial Port - A 8250x or 16550 communications port that usually has a rs232 9 or 25 pin connector available for modem. Internal modems have a serial port built onto the PC modem/board.
Title Bar - the horizontal bar at the top of a window. It usually has text that describes the window.
True Type - A scalable font that allows the user to size the font size to fit the window size.
Queue - A stacked list of events waiting for execution.
V.32 - A set of rules governing modem characteristics for
error free MNP/LAP-M communications.
V.42 - A software specification for modem Data Compression and an Error Control Protocol that provides 100% error free communications.
Xfer - Short for file transfer.
( This page intentionally left blank )
Documentation Update Required Form
If you have any comments regarding the quality or accuracy of this documentation please fill out the following sheet and send it to the address listed at the beginning of this document. Your comments, ideas and corrections are appreciated!
